Skip to content

[close - superseded by #27] docs: draft weekly changelog for flaky tests updates#25

Closed
mintlify[bot] wants to merge 1 commit into
mainfrom
mintlify/6e28f1f7
Closed

[close - superseded by #27] docs: draft weekly changelog for flaky tests updates#25
mintlify[bot] wants to merge 1 commit into
mainfrom
mintlify/6e28f1f7

Conversation

@mintlify
Copy link
Copy Markdown
Contributor

@mintlify mintlify Bot commented May 18, 2026

Summary

Drafts this week's changelog posts covering flaky tests features shipped since the April 30 entry.

Changes

  • New feature — Failure count monitor: flag tests as soon as they accumulate a configured number of failures on monitored branches.
  • New feature — Org-scoped test labels: tag, organize, and filter your test suite.
  • Update — Monitors can now apply labels to tests as an action instead of classifying them as flaky or broken.
  • Drafts live under changelog/ and are excluded from the docs site build via .mintignore (the published changelog lives on trunk.io).

Context

The previous changelog entry was "Merge Queue: Chrome Extension" on April 30, 2026. The flaky tests additions above were the user-facing product changes shipped during this window.

@samgutentag samgutentag mentioned this pull request May 18, 2026
Merged
@samgutentag
Copy link
Copy Markdown
Member

samgutentag commented May 18, 2026

Heads up — opened #27 which stacks on this branch and is required to actually surface these changelogs on the docs site:

  • This PR adds changelog/ to .mintignore, so the 3 drafts ship to the repo but don't render.
  • feat(changelog): host the canonical changelog on docs.trunk.io #27 reverses that, adds a changelog/index.mdx landing page using Mintlify <Update> blocks, swaps the sidebar "Changelog" link from https://trunk.io/changelog → local /changelog, and adds a hidden tab so the top-bar tab indicator stays sane on changelog pages.

Together they're a proposal to move the canonical changelog from the marketing site to docs.trunk.io. The trade-offs the team should weigh (discoverability vs duplication, SEO, audience, authoring workflow) are in #27's description.

Merging this PR alone is fine for staging the drafts, but it won't actually expose them to readers — that's #27.

@samgutentag samgutentag changed the title docs: draft weekly changelog for flaky tests updates [ready to merge] docs: draft weekly changelog for flaky tests updates May 19, 2026
@samgutentag
Copy link
Copy Markdown
Member

samgutentag commented May 19, 2026

Verification status (2026-05-19): live

Verified: customers can use this. Ready to publish.

  • Eng PR: none (changelog drafts for already-shipped features)
  • Flag: none
  • Signals: drafts describe failure count monitor, org-scoped test labels, and apply-labels monitor action. These features have been live for weeks (showLabelActions: true in ts/apps/e2e/flags.json; monitor framework docs already migrated).

@samgutentag
Copy link
Copy Markdown
Member

samgutentag commented May 19, 2026

Heads up — #27 has been rebased onto main and now contains the 3 changelog drafts from this PR plus the full 150-entry historical migration from marketing-site. It supersedes this PR. Once #27 lands, this one can be closed.

@samgutentag samgutentag changed the title [ready to merge] docs: draft weekly changelog for flaky tests updates [close - superseded by #27] docs: draft weekly changelog for flaky tests updates May 19, 2026
@samgutentag
Copy link
Copy Markdown
Member

samgutentag commented May 19, 2026

Consolidation (2026-05-19): superseded by #27, recommend closing.

This PR's content is already fully contained in #27. PR #27 shares this branch's commit (26f779c) and adds two more commits on top: the nav change and the canonical-changelog import. PR #27's base is main, so it can merge independently. No reason to keep both open.

Recommend closing. If the team decides not to host the changelog on docs.trunk.io, #27 can be closed and a slimmed-down version of just this PR's three drafts can be reopened.

@samgutentag samgutentag added ready to merge Verify docs PR: customers can use this. Ready to publish. changelog PR touches the changelog (auto-generated drafts, hosting, formatting, indexing). labels May 19, 2026
samgutentag added a commit that referenced this pull request May 22, 2026
@samgutentag @claude
docs(changelog): surface auto-generated changelog under native sideba…
9013524 
…r nav

Switch the "Changelog" anchor in the sidebar (and footer) from
https://trunk.io/changelog to a local /changelog landing page that
surfaces the auto-generated changelog drafts produced by the Mintlify
changelog feature (added in #25).

- `changelog/index.mdx` — landing page listing the 3 May 18 entries as
  Mintlify `<Update>` blocks, each linking to its full draft.
- `docs.json` — anchor + footer href swapped from external trunk.io URL
  to `/changelog`. New hidden `Changelog` tab claims ownership of
  `/changelog/*` routes so the top-bar tab indicator stays correct
  (without the tab, Mintlify falls back to the last visible tab —
  Code Quality — when on changelog pages).
- `.mintignore` — `changelog/` is commented out so the auto-generated
  drafts build and route locally.

Staged for team buy-in on moving the changelog from the marketing site
to the docs site. Stacked on #25 — needs that PR's 3 changelog drafts
to render correctly.

Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

changelog PR touches the changelog (auto-generated drafts, hosting, formatting, indexing). ready to merge Verify docs PR: customers can use this. Ready to publish.

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@samgutentag